SD - Surya-Damodhier - 2017-02-20 - 15361 - Spec - Backorder Rejection (Rizwan by 2017-04-11) #salesorders #wipdoc

SPECIFICATIONS

15361-Spec-Backorder Rejection

Purpose

New Era Cap does not want to ship back order quantities of six or less. To meet this need, a program is run each night which evaluates open orders, and rejects small backorder quantities or will prevent them from automatically dropping on delivery.The overnight batch job will not automatically create deliveries for orders which have a quantity of six or less for Materials that have had no previous delivery based on ATP. These units will go into a fixed allocation status and these deliveries will need to be manually created or unfixed and cancelled.

Admin Info

Purpose	BackOrder rejection
Requested By	Rizwan Shah
Spec Created By	Deepak Yasam
Spec Created Date	03/24/2017
Spec QA by	Surya Basa
Objects	ZSD_SMALLORD_REJ
Document Status	WIP

Estimates

Sl.No	Activity	Estimation in Hours
1	Research	08
2	Documentation	08
3	Development/ Config	40
4	Unit test in DEV	40
5	Unit test in QUA	40
6	Other activity
	TOTAL	136

References

Prior Tickets
[Provide links of prior associated Spec / Break Fix BOSS document(s)]
None

Documents
[Attach any document(s) received for the requirement(s)]
Backorder Rejection.pdf

Spec Changes

[List the changes made to program after the approval of the original requirement along with the Date on which the change request was received and the name of the initiator]

Sl.	Change Details	Requested By	Requested On	Notes if any

Functional Requirement

Purpose/WHY:
[Explain the purpose of the project and the reason why this requirement has come]
The delivery creation user exit and the backorder rejection program should be modified .
In Scope:
[List the activities to be included in scope]
Only the above exit and program in in scope.
Out of Scope:
[Out of scope activities]

Solution Summary

[Discuss this section with Requester and get approval prior to beginning work]

The delivery creation user exit that had BATCHUSER logic to stop the delivery creation if the qunatity is less than 6 should be commented.
The small order rejection program should be modified to consider the initial delivery for any of the size for the material instead of last size to fix the bug.

Below is the example that Dan provided to confirm the removal of BATCHUSER logic is enough instead of creating a new batch job with another user.

(1) Sales order is placed for 50 units
(2) 48 units are available
(3) 48 units are allocated, and a delivery for this quantity is created, PGIed, and subsequently invoiced by the nightly job
(4) The remaining 2 units are backorder, and the rejection job marks them rejected with code ZI
(5) Any subsequent delivery job will not deliver the backorder (even if quantity becomes available), as those items are rejected

Test Plan
[List test scenarios/cases to be executed here]

Test ID	Test Scenario		Expected Result
SD-001	1.Create a SO with multiple materials and multiple sizes.	Execute delivery creation and back order rejection program in background	The delivery shouldn't be created as no allocation is done for the SO
SD-002	1.Create a SO with multiple materials and multiple sizes. 2.Allocate single size of first material.		1. The delivery should be created for the allocated sizes. 2.Remaining sizes should be rejected with ZI rejection reason as the remaining open order qty is < or = 6.
SD-003	1.Create a SO with multiple materials and multiple sizes. 2.Allocate single size of first material.		1. The delivery should be created for the allocated sizes. 2.Remaining sizes should be rejected with ZI rejection reason as the remaining open order qty is < or = 6. 3.Delivery shouldn't be created for other materials as they are not allocated.
SD-004	1.Create a SO with multiple materials and multiple sizes. 2.Allocate only first material.		1. The delivery should be created for the allocated sizes. 2.Remaining sizes should be rejected with ZI rejection reason as the remaining open order qty is < or = 6. 3.Delivery shouldn't be created for other materials as they are not allocated.
SD-005	1.Create a SO with single material and multiple sizes. 2.Allocate first size of the material.		1. The delivery should be created for the allocated sizes. 2.Remaining sizes should be rejected with ZI rejection reason as the remaining open order qty is < or = 6.
SD-006	1.Create a SO with single material and multiple sizes. 2.Allocate second size of the material.		1. The delivery should be created for the allocated sizes. 2.Remaining sizes should be rejected with ZI rejection reason as the remaining open order qty is < or = 6.
SD-007	1.Create a SO with same material at multiple items. 2.Allocate single size of the first material.		1. The delivery should be created for the allocated sizes. 2.Remaining sizes should be rejected with ZI rejection reason as the remaining open order qty is < or = 6. 3.Delivery shouldn't be created for other materials as they are not allocated.
SD-008	1.Create a SO with multiple materials and multiple sizes. 2.Allocate certain sizes of the materials.		1. The delivery should be created for the allocated sizes. 2.Remaining sizes should be rejected with ZI rejection reason as the remaining open order qty is < or = 6. 3.Delivery shouldn't be created for other materials as they are not allocated.

Solution Details

[Provide complete technical details for configuration or programming here]

Issues

[List Issues / Bugs identified in configuration or development]